1. Home
  2. Vulnerabilities
  3. CVE-2025-21694
5.5
MEDIUM CVSS 3.1
CVE-2025-21694
Linux Kernel Softlockup in ProcFS
Description

In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in __read_vmcore (part 2) Since commit 5cbcb62dddf5 ("fs/proc: fix softlockup in __read_vmcore") the number of softlockups in __read_vmcore at kdump time have gone down, but they still happen sometimes. In a memory constrained environment like the kdump image, a softlockup is not just a harmless message, but it can interfere with things like RCU freeing memory, causing the crashdump to get stuck. The second loop in __read_vmcore has a lot more opportunities for natural sleep points, like scheduling out while waiting for a data write to happen, but apparently that is not always enough. Add a cond_resched() to the second loop in __read_vmcore to (hopefully) get rid of the softlockups.

INFO

Published Date :

Feb. 12, 2025, 2:15 p.m.

Last Modified :

Feb. 14, 2025, 3:46 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2025-21694 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Update the Linux kernel to resolve softlockups in fs/proc.
  • Update the Linux kernel to the latest version.
  • Apply the fix for softlockups in __read_vmcore.
  • Test the system for stability after the update.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-21694.

URL Resource
https://git.kernel.org/stable/c/649b266606bc413407ce315f710c8ce8a88ee30a Patch
https://git.kernel.org/stable/c/65c367bd9d4f43513c7f837df5753bea9561b836 Patch
https://git.kernel.org/stable/c/80828540dad0757b6337c6561d49c81038f38d87 Patch
https://git.kernel.org/stable/c/80da29deb88a3a907441fc35bb7bac309f31e713 Patch
https://git.kernel.org/stable/c/84c4ed15626574c9ac6c1039ba9c137a77bcc7f2 Patch
https://git.kernel.org/stable/c/a5a2ee8144c3897d37403a69118c3e3dc5713958 Patch
https://git.kernel.org/stable/c/cbc5dde0a461240046e8a41c43d7c3b76d5db952 Patch
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-21694 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-21694 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-21694 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2025-21694 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Feb. 14, 2025

    Action Type Old Value New Value
    Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Added CWE NIST NVD-CWE-noinfo
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.19.317 up to (excluding) 4.20 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.4.279 up to (excluding) 5.4.290 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.221 up to (excluding) 5.10.234 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.15.162 up to (excluding) 5.15.177 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.1.95 up to (excluding) 6.1.127 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.6.35 up to (excluding) 6.6.74 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.9.6 up to (excluding) 6.12.11 *cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.13:rc7:*:*:*:*:*:*
    Changed Reference Type https://git.kernel.org/stable/c/649b266606bc413407ce315f710c8ce8a88ee30a No Types Assigned https://git.kernel.org/stable/c/649b266606bc413407ce315f710c8ce8a88ee30a Patch
    Changed Reference Type https://git.kernel.org/stable/c/65c367bd9d4f43513c7f837df5753bea9561b836 No Types Assigned https://git.kernel.org/stable/c/65c367bd9d4f43513c7f837df5753bea9561b836 Patch
    Changed Reference Type https://git.kernel.org/stable/c/80828540dad0757b6337c6561d49c81038f38d87 No Types Assigned https://git.kernel.org/stable/c/80828540dad0757b6337c6561d49c81038f38d87 Patch
    Changed Reference Type https://git.kernel.org/stable/c/80da29deb88a3a907441fc35bb7bac309f31e713 No Types Assigned https://git.kernel.org/stable/c/80da29deb88a3a907441fc35bb7bac309f31e713 Patch
    Changed Reference Type https://git.kernel.org/stable/c/84c4ed15626574c9ac6c1039ba9c137a77bcc7f2 No Types Assigned https://git.kernel.org/stable/c/84c4ed15626574c9ac6c1039ba9c137a77bcc7f2 Patch
    Changed Reference Type https://git.kernel.org/stable/c/a5a2ee8144c3897d37403a69118c3e3dc5713958 No Types Assigned https://git.kernel.org/stable/c/a5a2ee8144c3897d37403a69118c3e3dc5713958 Patch
    Changed Reference Type https://git.kernel.org/stable/c/cbc5dde0a461240046e8a41c43d7c3b76d5db952 No Types Assigned https://git.kernel.org/stable/c/cbc5dde0a461240046e8a41c43d7c3b76d5db952 Patch
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Feb. 12, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in __read_vmcore (part 2) Since commit 5cbcb62dddf5 ("fs/proc: fix softlockup in __read_vmcore") the number of softlockups in __read_vmcore at kdump time have gone down, but they still happen sometimes. In a memory constrained environment like the kdump image, a softlockup is not just a harmless message, but it can interfere with things like RCU freeing memory, causing the crashdump to get stuck. The second loop in __read_vmcore has a lot more opportunities for natural sleep points, like scheduling out while waiting for a data write to happen, but apparently that is not always enough. Add a cond_resched() to the second loop in __read_vmcore to (hopefully) get rid of the softlockups.
    Added Reference https://git.kernel.org/stable/c/649b266606bc413407ce315f710c8ce8a88ee30a
    Added Reference https://git.kernel.org/stable/c/65c367bd9d4f43513c7f837df5753bea9561b836
    Added Reference https://git.kernel.org/stable/c/80828540dad0757b6337c6561d49c81038f38d87
    Added Reference https://git.kernel.org/stable/c/80da29deb88a3a907441fc35bb7bac309f31e713
    Added Reference https://git.kernel.org/stable/c/84c4ed15626574c9ac6c1039ba9c137a77bcc7f2
    Added Reference https://git.kernel.org/stable/c/a5a2ee8144c3897d37403a69118c3e3dc5713958
    Added Reference https://git.kernel.org/stable/c/cbc5dde0a461240046e8a41c43d7c3b76d5db952
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 5.5
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact